Empresas
Empleos
  • Sobre nosotros
  • Soluciones
    • Publicación de vacantes
      Publica tu vacante y recibe candidatos calificados en 48h.
    • Evaluación de candidatos
      500+ pruebas técnicas y psicológicas, más anti-fraude.
    • Headhunting
      Búsqueda ejecutiva a la medida de principio a fin.
    • Nómina + EOR
      Dispersión de nómina y EOR en más de 15 países de LATAM.
  • Precios
  • Empleos

0

229
Vistas
Next.js/Square API error: Fetch API cannot load. URL scheme "webpack-internal" is not supported

I'm having this error when trying to pull stock from Square API.

injectGlobalHook.js:1648 Fetch API cannot load webpack-internal:///./node_modules/@next/react-dev-overlay/lib/internal/ReactDevOverlay.js. URL scheme "webpack-internal" is not supported.

I'm converting my React.js project into Next.js, so I'm just trying to learn the differences between the two.

Initially, I pulled the data with a proxy in my config file to avoid a CORS Error, but knew that was just a workaround for the time being because I needed to hide the API_KEY.

Now I'm trying to call the API the right way in Next.js backend options with getServerSideProps

export async function getStaticProps() {
  const allStockObjects = await fetch(requests.fetchAllStock, {
    method: "GET",
    headers: headers,
  })
    .then((res) => res.json)
    .catch((err) => console.log(err));

  return {
    props: {
      allStockObjects,
    },
  };
}

Here is my export, but I have the exact same export in a Component with a POST request done the same way to the same Square API and it works perfectly fine.

I also check my APILogs on my Square Dashboard and the request never makes it to the API at all.

Not much online on this error or Square API for that matter, so I hope someone could help.

about 4 years ago · Juan Pablo Isaza
2 Respuestas
Responde la pregunta

0

This issue is caused by React Devtoools, specifically the setting Always parse hook names from source (may be slow) — if you turn this off when not needed it will prevent the error.

about 4 years ago · Juan Pablo Isaza Denunciar

0

I just ran into a similar issue. For reference I am taking Wes Bos's course on React/ GraphQL. To get past the issue I shut down the frontend and then deleted the .next folder. Then re-ran the frontend so a new .next folder gets generated. I also cleared the browser cache. After that the issue went away for me.

about 4 years ago · Juan Pablo Isaza Denunciar
Responde la pregunta
Encuentra empleos remotos

¡Descubre la nueva forma de encontrar empleo!

Top de empleos
Top categorías de empleo
Empresas
Publicar vacante Precios Comercial
Legal
Términos y condiciones Política de privacidad
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomiéndame algunas ofertas
Necesito ayuda